sdks/java/src/test/java/org/byteveda/taskito/ResourceTest.java (1)

108-224: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Missing coverage for REQUEST-scoped dependency resolution.

The new tests cover THREAD reuse/disposal and REQUEST freshness/disposal well, plus two negative dependency checks (THREAD→TASK, WORKER→THREAD). However, REQUEST is the newest and shortest-lived scope, and its most novel code path — resolving dependencies via requestContext/buildRequest (per context snippet 3) — is untested:

• No test verifies a REQUEST factory can successfully ctx.use(...) a WORKER/THREAD/TASK resource (positive path through requestContext).
• No test verifies that a TASK/THREAD/WORKER factory depending on a REQUEST-scoped resource is rejected (REQUEST is shorter-lived than all of these, per the "same- or longer-lived" dependency rule).

Given requestContext's dependency-resolution logic isn't exercised by perUse's no-op factory (ctx -> new Object()) in requestResourceFreshPerUse, this is currently unverified.

Example additions

`@Test`
`@Timeout`(30)
void requestFactoryCanUseTaskScopedResource(`@TempDir` Path dir) throws Exception {
    try (Taskito queue =
            Taskito.builder().url(dir.resolve("rrqok.db").toString()).open()) {
        queue.resource("perTask", ResourceScope.TASK, ctx -> new Object());
        queue.resource("perUse", ResourceScope.REQUEST, ctx -> ctx.use("perTask"));
        // ... assert Resources.use("perUse") resolves without throwing
    }
}

`@Test`
`@Timeout`(30)
void taskFactoryCannotUseRequestScopedResource(`@TempDir` Path dir) throws Exception {
    try (Taskito queue =
            Taskito.builder().url(dir.resolve("rtrq.db").toString()).open()) {
        queue.resource("perUse", ResourceScope.REQUEST, ctx -> new Object());
        queue.resource("perTask", ResourceScope.TASK, ctx -> ctx.use("perUse"));
        // ... assert ResourceException when using "perTask"
    }
}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@sdks/java/src/test/java/org/byteveda/taskito/ResourceTest.java` around lines
108 - 224, Missing coverage for REQUEST-scoped dependency resolution: add tests
around the REQUEST path in ResourceTest to exercise requestContext/buildRequest
with real dependencies. Create one positive test where a REQUEST resource (for
example, the perUse registration) successfully ctx.use(...) a WORKER, THREAD, or
TASK resource and assert it resolves correctly, and add a negative test showing
a TASK/THREAD/WORKER factory depending on a REQUEST-scoped resource throws
ResourceException. Use the existing ResourceScope, Resources.use, and
queue.resource patterns in the new test methods to keep the scope-dependency
rules covered.